script({
    files: "packages/sample/genaisrc/readme-updater.genai.mts",
    system: ["system", "system.assistant", "system.files"],
    tools: ["fs"],
    model: "large",
    temperature: 0.8,
})

const today = new Date()
const yyyy = today.getFullYear()
const mm = String(today.getMonth() + 1).padStart(2, "0")
const dd = String(today.getDate()).padStart(2, "0")
const formattedDate = `${yyyy}-${mm}-${dd}`

def("FILE", env.files)
defFileOutput("docs/src/content/docs/blog/drafts/*.mdx", "generated blog posts")

$`Create a blog post file that explains the GenAIScript source code in FILE.

- the title should be the intention of the script  as if the user wrote it, use simple words, keep it short, mention genai, wrap in quotes
- tell the motivation for the script.  Add a link to the script file using a GitHub URL.
- explain the script code line by line as if you were writing the script from scratch. Assume the reader is a beginner. Show the code being explained. Also explain prompts ($\`...\` line by line)
- explain all the code, don't skip any line. this is important
- add a section that explains how to run the script with the genaiscript cli. Do not explain how to install the cli, link to the documentation instead.
- be minimalistic, avoid jargon, use simple words

# Instructions

- use a technical blog tone, see https://dev.to/p/editor_guide
- Do not use <details> tag
- link to the github source URL if possible
- use a clear and engaging tone
- use emojis
- add authors in front matter as 'authors: genaiscript'
- do NOT generate <details> or <summary> tags
- add "draft: true" in the front matter
- add tags in frontmatter
- do not repeat topic
- set frontmatter date to ${formattedDate}
- avoid "genaiscript" in file title
- frontmatter tag should be an array
- do NOT repeat page title in markdown content
- save generate text to blog post drafts folder
- ignore existing blog posts
- avoid using "delve", "streamline"
- do not repeat or explain the script file top comment
- include canonical_url to genaiscript blog at https://microsoft.github.io/genaiscript/blog/<topic>
- use language "ts" for mts snippets and "js" for mjs snippets
- use markdown headers starting from level 2
- use lowercase characters, dashes for filenames
- when invoking the CLI, prefer using the script filename instead of the full path : "genaiscript run <filename_without_genai_extension>"
- if the script imports code from "genaiscript/runtime", explain what those imports do. The source is in file packages/cli/src/runtime.ts
- make sure to generate a filename for the blog post. The filename should be the same as the script filename without the "genai" extension. For example, if the script filename is "makeitbetter.genai.mjs", the blog post filename should be "makeitbetter.md"


# File information

- guides: docs/src/content/docs/guides/*.md*
- getting started: docs/src/content/docs/getting-started/*.md*
- reference documentation: docs/src/content/docs/reference/*.md*
- type definition: genaisrc/genaiscript.d.ts
- samples: packages/sample/genaisrc/*.genai.*s
- online documentation: https://microsoft.github.io/genaiscript/ . The routing is docs/src/content/docs/**/<route>.md* becomes https://microsoft.github.io/genaiscript/<route>.
- use links to online documentation
- github repository: https://github.com/microsoft/genaiscript . "main" is the default branch.

## Output

Render the output as a markdown file using
the FILE formats. Make sure the output code section as 5 back ticks.

`
